• Created by Unknown User (leslie.obourn), last modified on Aug 15, 2022


Questions for Teresa:

  1. You mentioned the worktag request framework is similiar to RBA - but is it also similar to the Gift worktag request framework?
  2. Notes:
    1. Would we allow multiple worktags on a request?  (e.g., a Spend Category & Revenue Category requires a Ledger Account - but assume the new Ledger Account would be a separate request).  
    2. Assume that values are provided for selection (e.g., a list of Ledger Accounts).  Will we need a value of 'New Ledger Account' if a new one is being requested? 
    3. Related Worktag Usage report/task to see which worktag types are required (e.g., Project requires Default Fund)
    4. Some Worktags require a bp and some don't. (Most do not have a bp - gift and project have a bp)
    5. Are worktags associated with orgs?  
    6. It appears there are subforms based on the worktag or hierarchy (draft with finance functional consultant)
  3. Estimate:
    1. Design of the pages/sub-forms
    2. Routing & Approvals - Is there any editing after submission?  Assume the  security groups currently exist (the work is happening manually now)
    3. Disposition requirements - who does it?  how many people involved?  BP Admin, Security Admin?
    4. Integration to create/update worktags?
  4. Next Steps:
    1. Pre-meeting with functional consultant (Sheryl, Jerry, Thor)
    2. Talk through with Teresa
  5. UVA has built a Worktag Validator with Boomi to confirm 
    1. Used by units that need to pre-validate before sending an EIB/Integration 
    2. Facilities needs a form with a barcode

It is a brand new app, but will have similar framework, where requests will have to be validated and approved and there will probably be integrations to set the new worktags up in Workday.

I like the hybrid approach.   Attached are some rough requirements from the Finance team.



Below are some other notes from the Finance team (I will say I believe the request for these worktags should be included.)

Hi, attached is a request template for new worktags and hierarchies. User can select the requested worktag/hierarchy and required information will change depending on the worktag/hierarchy chosen from the drop-down list.


Thomas Schneberger’s thoughts and questions related to process for each worktag are below:

Gift: not included in this template as we are using Workday Extend.

Grant: not included in this template as all request have to go through OSP and setup through Huron software.

Assignee: not included in this template. What is the exact timing and process for creating the Assignee worktag for new workers and inactivating terminated workers?

Location: not included in this template as new locations should come from space mgmt. system managed by FM. How will a new location worktag be created?

Internal Reference: not included in this template as those also come from FM. However, if other ISDs or units want to create any, would it come through us? Can add this if so.

Project: it’s included in the template. While FM will setup their own, are we setting up non-FM projects? Non-FM projects should route through Central Accounting & Reporting for input on default function/fund/etc if project is operational.  

Designated: all requests should route through Central Accounting & Reporting (and OFP&A?).

Spend/revenue Category: all requests should route through Central Accounting & Reporting and OFP&A. Need to know Cardinal hierarchy and UFM hierarchies to add them to.

Ledger Account: all requests should go through Central Accounting & Reporting.

Fund: all requests should go through Central Accounting & Reporting and OFP&A. Need to know Cardinal hierarchy and UFM Fund source group to add them to.

Function: all requests should go through Central Accounting & Reporting.

Cost Centers: Can be reviewed by support team for reasonableness, but I think a functional person should review these as well (Yvonne?). Don’t think there are any worktags in Oracle that aren’t reviewed by a functional person before setup.

Programs: Can be reviewed by support team for reasonableness, but I think a functional person should review these as well (Yvonne?). Don’t think there are any worktags in Oracle that aren’t reviewed by a functional person before setup.  

Activity: Can be reviewed by support team for reasonableness, but I think a functional person should review these as well (Yvonne?). Don’t think there are any worktags in Oracle that aren’t reviewed by a functional person before setup.  

BU: all requests should go through Central Accounting & Reporting.

Company: all requests should go through Central Accounting & Reporting

  • No labels